home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
ftp.cs.arizona.edu
/
ftp.cs.arizona.edu.tar
/
ftp.cs.arizona.edu
/
icon
/
newsgrp
/
group02b.txt
/
000147_icon-group-sender_Sun Dec 1 13:56:35 2002.msg
< prev
next >
Wrap
Internet Message Format
|
2003-01-02
|
1KB
Return-Path: <icon-group-sender>
Received: (from root@localhost)
by baskerville.CS.Arizona.EDU (8.11.1/8.11.1) id gB1KtVI28869
for icon-group-addresses; Sun, 1 Dec 2002 13:55:31 -0700 (MST)
Message-Id: <200212012055.gB1KtVI28869@baskerville.CS.Arizona.EDU>
X-Sender: whm@mail.mse.com
Date: Wed, 27 Nov 2002 22:25:44 -0700
To: icon-group@cs.arizona.edu
From: "William H. Mitchell" <whm@mse.com>
Subject: I don't know why nothing is popular
Errors-To: icon-group-errors@cs.arizona.edu
Status: RO
Here's a claim to consider: Of languages like Icon, Perl, Python, etc.,
NONE are popular with the average programmer.
I estimate that on average I write one Icon application every week or two
to help with some non-Icon project I'm working on. It might be text
massage, test case generation, a program to answer a question, etc.
I think that most programmers encounter some number of situations where
they could write a program to solve an intermediate problem but those
programs typically never get written. That's because they're too clumsy to
write in Java or C++ or VB, or whatever the programmer's bread-and-butter
language is, and the programmer doesn't know anything like Icon or Perl or
Python well enough to write the program in a time-efficient fashion.
That's pretty sad.